Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🤖 Synchronize branch release-next to upstream/main #529

Merged
merged 1 commit into from
Sep 23, 2024

Conversation

serverless-qe
Copy link

This automated PR is to make sure the forked project's release-next branch (forked upstream's main branch) passes a CI.

@serverless-qe serverless-qe added the kind/sync-fork-to-upstream Tag used for PRs that are automatically created to merge upstream changes label Sep 23, 2024
Copy link

openshift-ci bot commented Sep 23, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: serverless-qe
Once this PR has been reviewed and has the lgtm label, please assign cardil for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@serverless-qe
Copy link
Author

OCF Webhook is merging this PR

@serverless-qe serverless-qe merged commit 716079e into release-next Sep 23, 2024
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/sync-fork-to-upstream Tag used for PRs that are automatically created to merge upstream changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant